home *** CD-ROM | disk | FTP | other *** search
-
-
-
- - 1 -
-
-
-
- 4. _K_n_o_w_n__P_r_o_b_l_e_m_s__a_n_d__W_o_r_k_a_r_o_u_n_d_s
-
- This chapter lists the problems with using the the IRIS
- Performer 2.0.1 execution environment, _l_i_b_p_r and _l_i_b_p_f, and
- with the shared memory configurations.
-
- 4.1 _GGGG_eeee_nnnn_eeee_rrrr_aaaa_llll _IIII_ssss_ssss_uuuu_eeee_ssss
-
- +o When more than 512 textures are used in either IRIS GL
- or OpenGL on RealityEngine graphics subsystems, the
- hardware and or host-side software may become confused
- and in some cases, may falter completely and terminate
- the application. This is a graphics library limitation
- on the RealityEngine and does not exist on other types
- of graphics subsystems.
-
- +o IRIS GL based Performer 2.0 executables may encounter
- difficulties when executing multipipe on dual-head
- Indigo systems. This problem is not present in OpenGL
- applications. Check with SGI Customer Support for the
- latest advice if you encounter this problem and need to
- use IRIS GL rather than OpenGL.
-
- +o Although Performer supports it, OpenGL does not support
- different material color modes for front and back
- materials. When Performer encounters this case, it
- disables the material color mode for the back material.
-
- +o Remote IRIS GL/X operation (display of IRIS GL/X
- windows on remote systems) fails in many situations.
- Remote display should use pure IRIS GL windows or
- OpenGL operation.
-
-
-
- 4.2 _IIII_RRRR_IIII_XXXX_6666 _aaaa_nnnn_dddd _6666_4444_BBBB_iiii_tttt
-
- +o _S_t_a_t_i_s_t_i_c_s: The IRIS Performer CPU statistics class for
- accumulation of statistics on CPU usage are not yet
- implemented for IRIX6 operation (64bit or 32bit).
-
- +o _A_n_t_i_a_l_i_a_s_i_n_g: When it is not multisampling, _p_f_A_n_t_i_a_l_i_a_s
- can significantly degrade performance. Specifically,
- on non RealityEngine or InfiniteReality systems, use
- _p_f_A_n_t_i_a_l_i_a_s only for lines and points.
-
- +o _C_o_p_l_a_n_a_r _p_o_l_y_g_o_n_s: _p_f_D_e_c_a_l works only on machines that
- support the _s_t_e_n_c_i_l or _d_i_s_p_l_a_c_e_p_o_l_y_g_o_n command. The
- default decaling mode for PFDECAL_BASE uses
- _d_i_s_p_l_a_c_e_p_o_l_y_g_o_n instead of _s_t_e_n_c_i_l. This can
- significantly improve rendering performance but can
-
-
-
-
-
-
-
-
-
-
-
- - 2 -
-
-
-
- result in visual anomalies where layer polygons
- incorrectly "poke" through other geometry. If you wish
- to use stencil then specify the
- PFDECAL_BASE_HIGH_QUALITY token.
-
- +o _S_t_e_n_c_i_l: stencil is used for PFDECAL_BASE_HIGH_QUALITY
- and for pfStats mode PFSTATSHW_GFXPIPE_FILL. Stencil
- is not supported on all graphics platforms. Indy
- graphics platforms under IRIS GL operation do not
- support stencil. The Extreme graphics platforms
- support stencil with reduced depth buffer resolution so
- IRIS Performer will not allocate stencil bits in the
- default framebuffer configuration. While allocated by
- default, the allocation of extra stencil bits can also
- affect your depth resolution and number of samples for
- multisample on RealityEngine and InfiniteReality
- graphics platforms.
-
- +o _T_r_a_n_s_p_a_r_e_n_c_y: _p_f_T_r_a_n_s_p_a_r_e_n_c_y works only on machines
- that support either _b_l_e_n_d_f_u_n_c_t_i_o_n or _m_u_l_t_i_s_a_m_p_l_e
- (RealityEngine and InfiniteReality).
-
- +o _p_f_L_P_o_i_n_t_S_t_a_t_e: pfLPointStates offer advanced features
- for the sophisticated _l_i_g_h_t _p_o_i_n_t primitive for visual
- simulation applications. Some of the texturing modes
- may not be supported or currently working on mid-range
- or low-end graphics platforms.
-
- +o Since having other applications running can impact
- real-time performance, it's sometimes desirable to
- minimize the number of daemons and other processes. If
- you have problems achieving real-time behavior, try the
- _p_f_u_L_o_c_k_C_P_U utility code in _l_i_b_p_f_u_t_i_l. You might also
- try turning off the desktop support and other daemons
- that are not crucial to your application, e.g.:
-
- % touch ~/.disableDesktop
-
- or
-
- % mkdir ~/.desktop-<machinename>
-
- % touch ~/.desktop-<machinename>/nodesktop
-
- and for total removal do:
-
- % chkconfig desktop off
-
- % chkconfig objectserver off
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 3 -
-
-
-
- % chkconfig directoryserver off
-
- % chkconfig fontserver off
-
-
- 4.3 _llll_iiii_bbbb_pppp_ffff
-
- +o _C_h_a_n_n_e_l _f_a_d_e _L_O_D _a_t_t_r_i_b_u_t_e_s _a_n_d _m_i_x_e_d _g_r_a_p_h_i_c_s
- _c_o_n_f_i_g_u_r_a_t_i_o_n_s: Channel fade LOD attributes are set in
- the application process. The existence of
- multisample,required for fade LOD, is tested at the
- time that the attributes are set with _p_f_C_h_a_n_L_O_D_A_t_t_r.
- This test for multisample uses the application process
- window system connection (_p_f_O_p_e_n_W_S_C_o_n_n_e_c_t_i_o_n) or else
- the DISPLAY environment variable to select a screen for
- determining graphics configuration, instead of testing
- the current window of the pfChannel. In a multipipe
- environment where one graphics pipeline has multisample
- and one does not, the application process needs to have
- a window system connection or DISPLAY that points to
- the pipeline with multisample, in which case the non-
- multisample pfChannels will try to use fade LOD. In a
- multi-window environment, windows without multisample
- on a system with multisample will try to use fade LOD.
-
- +o _G_a_n_g_d_r_a_w _a_n_d _c_u_r_s_o_r _l_o_a_d_i_n_g _o_n _R_e_a_l_i_t_y_E_n_g_i_n_e: Loading
- the cursor with ganged swapbuffers (external swapready
- wire) hangs graphics on RealityEngine. Workaround:
- don't load the cursor and use a full screen window when
- using ganged swapbuffers.
-
- +o _O_p_e_n_G_L _P_r_o_j_e_c_t_i_v_e _T_e_x_t_u_r_e_d _p_f_L_i_g_h_t_S_o_u_r_c_e_s: Under OpenGL
- operation, pfLightSources using a projected texture do
- not work.
-
-
- 4.4 _llll_iiii_bbbb_pppp_ffff_uuuu_tttt_iiii_llll
-
- +o No known problems.
-
-
- 4.5 _llll_iiii_bbbb_pppp_ffff_dddd_bbbb
-
- +o _p_f_d_L_o_a_d_F_i_l_e__d_x_f: The DXF loader does not fully support
- the format.
-
- +o _p_f_d_L_o_a_d_F_i_l_e__s_g_o: The SGO loader does not support
- triangle strips.
-
-
- ns
-
-
-
-
-
-
-
-
-
-
-
- - 4 -
-
-
-
- 4.6 _N_o_t_e_s__o_n__S_h_a_r_e_d__M_e_m_o_r_y__C_o_n_f_i_g_u_r_a_t_i_o_n_s
-
- IRIS Performer requires shared memory and uses a memory-
- mapped file, the location of which depends on the value of
- the PFTMPDIR environment variable:
-
- +o If PFTMPDIR is not set, Performer uses /_d_e_v/_z_e_r_o as the
- default. Running an application in this configuration:
-
- - Uses swap space
-
- - Does not require disk space until main memory is
- exhausted
-
- - Is faster than using a regular memory mapped file
- via PFTMPDIR
-
- - Causes IRIX to kill the process(es) and log an
- error to the console if the application runs out
- of space for shared memory in the swap partition.
-
- +o If PFTMPDIR is set, Performer creates files in the
- specified directory. Running an application in this
- configuration:
-
- - Requires disk space even before main memory is
- exhausted
-
- - Is slower than /_d_e_v/_z_e_r_o because it touches the
- disk
-
- - Produces appropriately sized core dump files with
- no limit set by IRIS Performer
-
- - Might cause a core dump from a segmentation
- violation inside _p_f_M_a_l_l_o_c if the application runs
- out of space for shared memory in the file system
- containing PFTMPDIR
-
- - PFTMPDIR should be set only to a directory on a
- local file system.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-